Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

correct mimetype location to follow the shared mime info specification #681

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

correct mimetype location to follow the shared mime info specification #681

wants to merge 1 commit into from

Conversation

Jan200101
Copy link
Contributor

according to the shared-mime-info specification it should be installed into the packages folder:

Each application that wishes to contribute to the MIME database will install a single XML file, named after the application, into one of the three /packages/ directories (depending on where the user requested the application be installed). After installing, uninstalling or modifying this file, the application MUST run the update-mime-database command, which is provided by the freedesktop.org shared database[SharedMIME].

Unified system | Shared MIME-info Database

I saw that this change was made for FreeBSD but they seem to support the shared mime database
image

@LIJI32
Copy link
Owner

LIJI32 commented Jan 23, 2025

It's probably wise to uninstall the copy outside of packages/ that might have been there from a previous installation in the install target, otherwise you'd have two competing definitions.

@Jan200101
Copy link
Contributor Author

I'm not so sure...
the codepath is only accessed when DESTDIR is set which I don't think a regular user would do, only system packages appear to be impacted by this changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Jan200101 @LIJI32